Context based cache eviction

ABSTRACT

A method, medium, and system to receive a request to add a resource to a cache, the resource including a data object and a context item key associated with the resource and uniquely identifying a context of use referenced by the context item key; determine whether the resource is stored in the cache; store, in response to the determination that the resource is not stored in the cache, the resource in the cache; and add the context item key of the resource stored in the cache to a record of reference list of resources.

BACKGROUND

Cache replacement policies or cache policies may be used by a computingsystem or device to manage a cache memory for data stored therein. Insome instances, the cache policy is invoked when the cache is full andone or more data items need to be removed from the cache to make roomfor new data items. The cache policy and a controller governingimplementation of the cache policy may operate to determine which dataitems or resources are evicted from the cache to make room for the newdata items.

Commonly used eviction policies are based on a data resource's age andusage (e.g., a “Least Recently Used” (LRU) cache eviction policy).However, such policies do not consider or take into account therelevance of the resource to the system user/s. Accordingly, a LRU cachepolicy may lead to the eviction of resources that are still needed byusers even though they may be accessed less recently than other dataresources. Eviction of such resources may lead to increased responsetimes for users, and negatively affect an overall system, application,or device performance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system, according to some embodiments;

FIG. 2 is an illustrative depiction of a reference list of references,according to some embodiments;

FIG. 3 is a flow diagram of a process, in accordance with someembodiments;

FIG. 4 is a flow diagram of a process, according to some embodiments;and

FIG. 5 is a block diagram of a computing device, in accordance with someembodiments.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a system 100, according to some embodimentsherein. System 100 represents a logical architecture for describingprocesses and a framework for a cache manager that provides a mechanismto evict data items from a cache based on a relevance or context of useassociated with the data items. Actual implementations of system 100 mayinclude more or different components arranged in other manners than thatshown in FIG. 1.

System 100 includes an application server 105 to provide resources fromdata sources 110, 115, and 120 to client devices 125, 130, and 135. Datasources 110, 115, and 120 may be located remotely from applicationserver 105 and/or client devices 125, 130, and 135. In some instances,application server 105 may receive a request to provide a resource fromdata source 110 to client device 125. Application server 105 may operateto retrieve the requested resource from data source 110 and transmit therequested resource to client device 125. In some aspects, applicationserver 105 may store the resource in repository 140. Unless otherwisestated, the resources herein may be of any data type and data structureincluding, but not limited to, a text file, an image file, an audiofile, a structured data file, a video, a file containing unstructureddata, a multimedia file, a hypertext markup language file, a message, anotification, a database item or object, combinations thereof, and otherdata structures without limit.

In some embodiments, one or more of client devices 125, 130, and 135 maybe mobile computing device such as smart phone that includes a telephonefunctionality and an ability to execute applications stored thereon. Theclient devices may be embodied as other devices and systems other than asmartphone. In some instances, an application such as an email client,calendar application, a social media application, business application,or a browser running on the client device may initiate a request for aresource from application server 105.

In an effort to improve performance (e.g., responsiveness) associatedwith retrieving and storing resources loaded from remote locations,requested resources may be stored locally in a cache of the clientdevices making the requests for the resources. In some instances,including but not limited to scenarios where the client devices aresmart phones, client devices 125, 130, and 135 may have a relativelylimited amount of cache available for storing the resources. In someaspects, the size of the cache may vary from one client device to a nextclient device. Given the limited amount of cache and/or theunpredictability of cache that may be available in a client device,performance of an application running on the client devices 125, 130,and 135 may be less than optimal. For example, operating performance ofa particular application on a client device with limited cache may beslow since the client device may not be able to efficiently store itemsin cache where they may be quickly accessed in a manner that is relevantto the use of the resources by the subject application.

In some instances, application server 105 may store the requestedresources in its cache (not shown) for a future use in an effort toimprove performance by having the resources available in cache for fastretrieval, as opposed to fetching the resources from remote data sources110, 115, and 120 or a disk based storage location (e.g., repository140) each time the resource is requested. Although application servermay have a relatively large cache as compared to clients 125, 130, and135, the application server's cache may be quickly filled based on, forexample, the number of clients it services and the number of resourcerequests those plurality of clients invoke.

In some aspects, a resource may include a data object (e.g., an imagefile, a document, an email message, etc.) and an object key. The objectkey is a unique identifier for the data object. In some instances, theobject key may be generated by an application, a database, or a memorymechanism. In some embodiments herein, a context item key may beassociated with the resource. The context item key may be a uniqueidentifier of a context of use that is referenced by the context itemkey.

In some embodiments, the context of use referenced by a context item keymay vary depending on a particular application, use-case, and type ofresource with which the context item key is associated. For example,regarding a communication application concerned with emailcommunications and meetings for a user, a context item key may beassociated with each email message and each meeting relating to theuser. Since the context item key is a unique identifier of the contextof use that is referenced by the context item key, each email meetingand meeting is uniquely identified by its referencing context item key.

FIG. 2 is an illustrative example of a reference list of resources 200.As used herein, a reference list of resources may be implemented by aninstance of a data structure such as, for example, a file, a record, adatabase object, a database table, etc. Reference list of resources 200is a logical representation of a reference list and an actualimplementation of the reference list of resources may include more ordifferent aspects, configurations, features, etc. than those depicted inFIG. 2. Regarding FIG. 2, the reference list of resources 200 includes afield 205 for a data object, a field for an object key that uniquelyidentifies the data object at 210, and a context item key field 215 thatis a unique identifier of a context of use that is referenced by thecontext item key and associated with the data object 205. For example, aresource may include data object 220 that is a profile (e.g.,biographical summary) of John Doe includes an object key 225 thatuniquely identifies that data object based on some convention. Theresource of data object 220 further includes a context item key 230(mtg_(—)001) that is a unique identifier of a context of use referencedby the context item key. In this instance, the context of use forcontext item key 230 is a first meeting. The user “John Doe” isassociated with the first meeting (mtg_(—)001) because a communicationapplication including implementations of some embodiments herein isaware of an upcoming meeting the user is scheduled to attend. It isnoted that the user “John Doe” (data object 220) is also associated withanother context item key 235 (meeting “mtg_(—)003”). Likewise, the dataobject 240 of a profile of user “Sue Smith” is associated with an objectkey 245 and a context item key 250 (meeting “mtg_(—)002”); and the dataobject 255 of an avatar of user “R. Jones” is associated with an objectkey 260 and the first context item key 230 (meeting “mtg_(—)001”).

In some embodiments, the profiles, avatars, and other data objects anditems associated with different people may be requested and retrievedfrom one or more data sources in connection with using a communicationapplication to schedule a meeting with those people by the application.The requested the profiles, avatars, and other data items or resourcesmay be stored in a cache. In some aspects, the communication applicationmay be executing on a client device (e.g., smartphone 130) or a server(e.g., application server 105). In some embodiments, portions of theapplication may be operating on both the client device and the server.Accordingly, the requested data resources such as, for example, theprofiles, avatars, and other data items may be stored in a cache of theclient device or the server, as appropriate per the application.

In some aspects, the application may determine that a meeting isrelevant until an end time of the meeting. When the meeting is no longerrelevant, the application may notify a cache manager or controllerimplementing a context-aware cache eviction policy or mechanism herein.In response to the notification, the cache manager or controllerimplementing a context based cache eviction policy or mechanism hereinmay proceed to evict data items no longer deemed relevant from thecache. In this manner, the cache may be efficiently used for storingdata that is relevant to its use. In some embodiments, an application,service, device, or system implementing the processes disclosed hereinmay determine a relevance associated with a context item key.

Referring to FIG. 2, a context item key may be removed from referencelist of resources 200 when the context of use (e.g., meeting mtg_(—)001)referenced by the context item key is no longer relevant. For example,context item key 230 may be deleted after the first meeting (mtg_(—)001)has occurred or ended. Once ended, the meeting is no longer relevant,according the communication application of the present example.According to some embodiments, data object 255 may then be deleted fromthe reference list of resources once all of its associated context itemkey(s) are deleted. An absence of context item keys associated with adata object may indicate that the data object is not relevant.Accordingly, the data object having no associated context item keys maybe evicted (deleted) from the cache. Continuing the present example,after the first meeting (mtg_(—)001), referenced by context item key230, occurs and context item key is removed from the reference list ofresources, data object 255 may be deleted from cache since it has noother context item keys associated with it. However, data object 220(i.e., the “Profile of John Doe”) is not deleted after the occurrence ofthe first meeting and the removal of the context item key 230 from thereference list of resources because context item key 235 is stillassociated with data object 220.

In some embodiments, the present disclosure may provide and define aframework for a cache manager or other controller that provides anapplication programming interface (API) for an application. The API maybe embedded in a mobile application and in a server-side application insome embodiments to insert and remove resource items to and from cache.

FIG. 3 is a flow chart of a process 300, in accordance with someembodiments herein. In some embodiments, various hardware elements ofsystem 100 execute program instructions to perform process 300. In someembodiments, hard-wired circuitry may be used in place of, or incombination with, program instructions for implementation of processesaccording to some embodiments. Embodiments are therefore not limited toany specific combination of hardware and software.

Prior to operation 305, an application executing on a mobile or otherclient device or a server-side computing device (e.g., an applicationserver) may be developed and deployed to the device(s) to implementprocess 200. At operation 305, a request to add a resource to a cache ofthe device may be received. For example, the request may be received bya client device having a cache. Control of the cache may be managed by acache manager or other controller. In some embodiments, management ofthe cache may be performed by other types and implementations ofhardware and software, including a general or specialized processor. Inaccordance with other aspects herein, the resource in the requestincludes an indication of a context item key associated with theresource.

In response to receiving the request to add the resource to the cache,the cache manager or other controller may determine whether the resourceis already stored in the cache at operation 310. In the instance theresource is already stored in the cache, the context item key associatedwith the resource in the request may be added to a resource referencelist at operation 330. In some aspects, the resource reference listincludes references to the resources stored in the device's cache,including the stored data items, the corresponding identifiers of thestored data items (i.e., an object key), and the context item key(s)associated with each data item stored in cache that references a contextof use for the data items.

In an instance the resource is not already stored in the cache asdetermined at operation 310, process 300 proceeds to operation 315. Atoperation 315, a determination is made whether the device's cache hassufficient space to store the resource of the request. Operation 315 mayinclude determining or checking the current size of the cache space, thesize of the resource, and a maximum allowable cache size for the cache.If it is determined at operation 315 that there is sufficient space toaccommodate the resource (i.e., cache size+resource size<maximum cachesize), process 300 may proceed to operation 325 where the resource isstored in the cache. In the instance it is determined that there is notsufficient space to accommodate the resource, process 300 may proceed tooperation 320 where a resource is removed (i.e., evicted) from the cachein an effort to free cache space for the new resource including in therequest received at operation 305.

In some embodiments, operation 320 includes evicting resources from thecache based, at least in part, on the context relevance of the resourcesstored in the cache. In some embodiments, each resource may have aresource relevance score associated therewith. The resource relevancescore may provide an indication of a total relevance value for a givenresource based on all of the context item keys associated with the givenresource, where each context item key has an associated relevance score.For example, referring to FIG. 2, resource 220 may have a resourcerelevance score of 2 and each of resources 240 and 255 may have aresource relevance score of 1, where each context item key referencing ameeting has an associated relevance score of 1.

In some embodiments, the relevance score for a context of use referencedby a context item key may be determined by an application implementingaspects of the present disclosure. For example, a first application mayassign a relevance score of 1 to every meeting, notwithstanding how farin the future the meeting is scheduled to occur, the meeting'sparticipants, the meeting's subject matter, the number of participantsin the meeting, and other factors. In some embodiments, one or more ofthese or other factors may be used by a second application to assign aweight to the relevance score for each context item key such that, forexample, a context item key may have a relevance score of 0.5, 1.0, 1.2,1.8 or other values depending on the value the application determinesfor each context item key.

In some embodiments, the removing of a resource from cache at operation320 may include removing a resource having a lowest resource relevancescore from the cache before removing a resource having a higher resourcerelevance score. In this manner, the “least” relevant items may beremoved from the cache before “more” relevant are evicted from thecache, where the relative relevance of a resource is indicated by theresource relevance score that provides an indication of a totalrelevance value for a given resource based on all of the context itemkeys associated with the given resource and each context item key has anassociated relevance score

Operations 315 and 320 may be repeated until it is determined atoperation 315 that there is sufficient space to accommodate the resourcein the cache. Process 300 may then proceed to operation 325 where theresource is stored in the cache.

At operation 330, the context item key associated with the request andthe resource therein may be added to a resource reference list atoperation 330. Continuing with process 300 from operation 330, operation335 may include updating the resource relevance score for the resourcereferenced in the request. In some embodiments, the updating of theresource relevance score for the resource may comprise including thevalue of the relevance score for the context item key associated withthe resource in the request in the determination or calculation of theresource relevance score for the resource.

In some aspects, process 300 may comprise part of another process(es).This aspect is indicated by the arrows leading into and out of the flowdiagram of FIG. 3. In some aspects, process 300 may be used, at least inpart, in combination with other cache eviction policies and mechanisms.For example, the context based cache eviction process of FIG. 3 may beimplemented, at least some aspects thereof, in combination with a “leastfrequently used” cache eviction policy by a system, device, or service.

FIG. 4 is a flow diagram of a process 400, in accordance with someembodiments herein. In some embodiments, various hardware elements ofsystem 100 execute program instructions to perform process 400. In someembodiments, hard-wired circuitry may be used in place of, or incombination with, program instructions for implementation of processesaccording to some embodiments. Embodiments are therefore not limited toany specific combination of hardware and software.

Prior to operation 405, an application executing on a mobile or otherclient device or a server-side computing device (e.g., an applicationserver) may be developed and deployed to the device(s) to implementprocess 400. In some embodiments, aspects of the context based cachingpolicy disclosed herein may be embodied in a API for an application(e.g., a mobile device application or a server-side application) and mayinclude a functionality to provide a notification of a context change.In some aspects, a request to remove a context item may be received by adevice, system, or service. In some aspects, the request to remove acontext item may be initiated or in response to a notification of acontext change from an application. In some embodiments, thenotification of the context change may be implemented as a email orother type of message.

In some aspects, the request to remove a context item may be received bya cache manager of a device or system that manages a cache associatedwith the system or device, in accordance with the present disclosure.

The request to remove the context item may include or reference acontext item key. It is noted that the context item keys herein may beunique identifiers of a context of use referenced by the context itemkey.

For each resource stored in a cache and referencing the context item keyidentified with the request of operation 405, process 400 may performoperations 410-430. Referring to FIG. 2 as an example, it is noted thata request to remove the context item related to a meeting (e.g.,“mtg_(—)001”) corresponding to context item 230 may include tworesources. Resources 220 and 255 are both associated with the context ofuse of context item key 230 (i.e., mtg_(—)001). Accordingly, operations410-430 may be traversed regarding both resource 220 and resource 255.

At operation 410, the context item key corresponding to the request ofoperation 405 may be removed from a resource reference list (e.g., FIG.2, resource reference list 200) managed by a cache controller or otherprocessor. The cache manager may operate to remove the associationbetween the context item key and the particular resource being operatedon in operation 410.

At operation 415, a determination is made whether the reference list ofreferences is empty of context item keys associations for the resource.For example, referring to FIG. 2 it is noted that after removal ofcontext item key 230, resource 220 will still have another context itemkey associated therewith. However, resource 255 will not have any othercontext item keys associated with it after the removal of context itemkey 230 from the reference list of resources 200.

In an instance it is determined that the reference list of references isempty of (other) context item key associations for the resource, process400 proceeds to operation 420. At operation 420, the resource with no(other) context item key associations may be removed (i.e., evicted)from the cache. A resource without any context item key associations maybe an indication that the resource is no longer relevant, at least tothe application, device, system, or service implementing the contextbased cache eviction policy herein.

In an instance it is determined that the reference list of references isincludes other context item key associations for the resource, process400 proceeds from operation 415 to operation 425. At operation 425, theresource relevance score for the resource with other context item keyassociations may be updated. This resource (e.g., resource 220 of FIG. 2with remaining context item key association 235) may have its resourcerelevance score updated to account for the removal of context item key230 from the reference list of resources 200.

Process 400 may proceed from operations 420 and 425 to operation 430. Atoperation 430, a decision may be made to determine whether the referencelist of resources is empty of resources. If the reference list ofresources is empty of resources, the process may proceed to 435 that maybe a termination point or other processes. If the reference list ofresources is not empty of resources, process 400 may proceed to a pointbefore operation 410 so that operations 410-430 may be performed foreach remaining resource in the reference list of resources.

In some aspects, process 400 may comprise part of another process(es).This aspect is indicated by the arrows leading into the flow diagram ofFIG. 4 and the optional termination point 435. In some aspects, process400 may be used, at least in part, in combination with other cacheeviction policies and mechanisms.

FIG. 5 is a block diagram overview of a system or apparatus 500according to some embodiments. System 500 may be, for example,associated with any of the devices described herein, including forexample an application server (e.g., FIG. 1, 105) and a client device(FIG. 1, 125), in accordance with processes disclosed herein. System 500comprises a processor 505, such as one or more commercially availableCentral Processing Units (CPUs) in the form of one-chip microprocessorsor a multi-core processor, coupled to a communication device 520configured to communicate via a communication network (not shown in FIG.5) to another device or system (e.g., an agent device and one or moresensor sets). In the instance system 500 comprises a server or a clientdevice (e.g., supporting context based cache eviction functions andservices provided by a cache controller), communication device 520 mayprovide a mechanism for system 500 to interface with another device,system, or service (e.g., another server, controller, and clientdevice). System 500 may also include a cache 510, such as RAM memorymodules. The system further includes an input device 515 (e.g., atouchscreen, mouse and/or keyboard to enter content) and an outputdevice 525 (e.g., a touchscreen, a computer monitor to display, a LCDdisplay).

Processor 505 communicates with a storage device 530. Storage device 530may comprise any appropriate information storage device, includingcombinations of magnetic storage devices (e.g., a hard disk drive),optical storage devices, solid state drives, and/or semiconductor memorydevices. In some embodiments, storage device 530 may comprise a databasesystem, including in some configurations an in-memory database.

Storage device 530 may store program code or instructions 535 that mayprovide computer executable instructions for managing a cache by a cachecontroller, in accordance with processes herein. Processor 505 mayperform the instructions of the program instructions 535 to therebyoperate in accordance with any of the embodiments described herein.Program instructions 535 may be stored in a compressed, uncompiledand/or encrypted format. Program instructions 535 may furthermoreinclude other program elements, such as an operating system, a databasemanagement system, and/or device drivers used by the processor 505 tointerface with, for example, peripheral devices (not shown in FIG. 5).Storage device 530 may also include data 540 such as a reference list ofresources. Data 540 may be used by system 500, in some aspects, inperforming one or more of the processes herein, including individualprocesses, individual operations of those processes, and combinations ofthe individual processes and the individual process operations.

All systems and processes discussed herein may be embodied in programcode stored on one or more computer-readable media. Such media mayinclude, for example, a floppy disk, a CD-ROM, a DVD-ROM, a Flash drive,magnetic tape, and solid state Random Access Memory (RAM) or Read OnlyMemory (ROM) storage units. Embodiments are therefore not limited to anyspecific combination of hardware and software.

Examples of a use-case herein have primarily focused on animplementation of the context based cache eviction policy and frameworkby a communication application concerned with meeting schedules. It isnoted that this is just one example and the cache policy disclosedherein may be implemented by other types of applications, including butnot limited to a email application that determines a relevancy of emailresources (e.g., email messages) assigns a context item key to the emailresources indicative of a relative relevancy of the particular emailresources. For example, the application may determine the weight orrelevancy value for an email message by examining and considering theage of the email message, the subject matter of the email message, thenumber of recipients of the email message (e.g., more recipients mayindicate a less relevant message as opposed to a message addressed to afew or a single recipient), a group of recipients for the email message,a importance/priority associated with the email message, and otherfactors that may be considered alone or in combination with each other.Some other types of applications that may incorporate aspects of thepresent disclosure include social network applications, businessdatabase management related systems and services (e.g., enterpriseresource planning, human resource planning, product lifecyclemanagement, etc.)

In some embodiments, a framework for providing the context based cacheeviction policy disclosed herein may be embedded in an application. Adeveloper of the application may define which data items (i.e.,resources) will be placed in a cache and the context item (e.g., contextitem keys) that will reference or otherwise relate to the data items tobe stored in the cache. In some aspects, the application developer orother responsible entity may define the “relevance” of a particularcontext of use.

In some embodiments, aspects herein may be implemented by anapplication, device, or system to manage cache in a consistent manneracross different devices, effectively across an entire domain.

Although embodiments have been described with respect to web browserdisplays, note that embodiments may be associated with other types ofuser interface displays. For example, a user interface may be associatedwith a portable device such as a smart phone or a tablet computingdevice (“tablet”), with a user interface element.

The embodiments described herein are solely for the purpose ofillustration. Those in the art will recognize other embodiments whichmay be practiced with modifications and alterations.

What is claimed is:
 1. A method implemented by a computing system inresponse to execution of program instructions by a processor of thecomputing system, the method comprising: receiving a request to add aresource to a cache, the resource including a data object and a contextitem key associated with the resource and uniquely identifying a contextof use referenced by the context item key; determining whether theresource is stored in the cache; storing, in response to thedetermination that the resource is not stored in the cache, the resourcein the cache; and adding the context item key of the resource stored inthe cache to a record of a reference list of resources.
 2. A methodaccording to claim 1, further comprising: determining whether there issufficient free space in the cache to store the resource; and removing,in response to the determination that there is not sufficient space inthe cache to store the resource, at least one other resource from thecache until there is sufficient space in the cache to store theresource.
 3. The method of claim 2, wherein the removing comprisesremoving a resource having a lowest resource relevance score from thecache before removing a resource having a higher resource relevancescore, the resource relevance score providing an indication of a totalrelevance value for a given resource based on all of the context itemkeys associated with the given resource, where each context item key hasan associated relevance score.
 4. The method of claim 1, wherein theresource further comprises a relevance score associated with the contextof use referenced by the resource's context item key.
 5. The method ofclaim 4, further comprising updating a resource relevance score for theresource to include the relevance score for the context item keyreceived in the request, the resource relevance score providing anindication of a total relevance value for a given resource based on allof the context item keys associated with the given resource, where eachcontext item key has an associated relevance score.
 6. The method ofclaim 1, wherein the record of the reference list of resources ismanaged by at least one of a mobile device application and a server-sideapplication.
 7. The method of claim 1, wherein the request to add theresource to a cache is received from an application.
 8. A non-transitorymedium storing processor-executable program instructions, the mediumcomprising program instructions executable by a computer to: receive arequest to delete a context item key from a record of a reference listof resources associated with at least one resource that is stored in acache and referenced in the reference list of resources; deleting thecontext item key included in the request from the reference list ofresources; determining, for each resource referenced in the referencelist of resources, whether at least one other context item key ispresent in the reference list of resources for the respective resource;removing, in response to the determination for each resource referencedin the reference list of resources that there is not at least one othercontext item key present in the reference list of resources, therespective resource from the cache; and saving the record of thereference list of resources.
 9. The medium of claim 8, furthercomprising updating, in response to the determination for each resourcereferenced in the reference list of resources that there is at least oneother context item key present in the reference list of resources, aresource relevance score for the respective resources stored in thecache, the updated resource relevance score providing an indication of atotal relevance value for a given resource based on all of the contextitem keys currently associated with the given resource, where eachcontext item key has an associated relevance score.
 10. The medium ofclaim 8, wherein the record of the reference list of resources ismanaged by at least one of a mobile device application and a server-sideapplication.
 11. The medium of claim 8, wherein the request to removethe context item key is received from an application.
 12. A systemcomprising: a computing device comprising: a memory storingprocessor-executable program instructions; and a processor to executethe processor-executable program instructions to cause the computingdevice to: receive a request to add a resource to a cache, the resourceincluding a data object and a context item key associated with theresource and uniquely identifying a context of use referenced by thecontext item key; determine whether the resource is stored in the cache;store, in response to the determination that the resource is not storedin the cache, the resource in the cache; add the context item key of theresource stored in the cache to a record of a reference list ofresources.
 13. A system according to claim 12, further comprising theprocessor to execute the processor-executable program instructions tocause the computing device to: determine whether there is sufficientspace in the cache to store the resource; and remove, in response to thedetermination that there is not sufficient space in the cache to storethe resource, at least one other resource from the cache until there issufficient free space in the cache to store the resource.
 14. The systemof claim 12, wherein the removing comprises removing a resource having alowest resource relevance score from the cache before removing aresource having a higher resource relevance score, the resourcerelevance score providing an indication of a total relevance value for agiven resource based on all of the context item keys associated with thegiven resource, where each context item key has an associated relevancescore.
 15. The system of claim 12, wherein the resource furthercomprises a relevance score for the context item key referenced by theresource's context item key.
 16. The system of claim 15, furthercomprising the processor to execute the processor-executable programinstructions to cause the computing device to update a resourcerelevance score for the resource to include the relevance score for thecontext item key received in the request, the resource relevance scoreproviding an indication of a total relevance value for a given resourcebased on all of the context item keys associated with the givenresource, where each context item has an associated relevance score. 17.The system of claim 12, wherein the record of the reference list ofresources is managed by at least one of a mobile device application anda server-side application.
 18. The system of claim 12, wherein therequest to add the resource to a cache is received from an application.